Fix JSON field names for vm-configuration and user-data#128427
Fix JSON field names for vm-configuration and user-data#128427v-dirichards merged 1 commit intoMicrosoftDocs:mainfrom
Conversation
|
@hyperfinitism : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. @Mishih |
|
Learn Build status updates of commit 0850b12: ✅ Validation status: passed
For more details, please refer to the build report. |
The JSON field names of the RuntimeClaims are kebab-case, not snake_case. Signed-off-by: Takuma IMAMURA <[email protected]>
0850b12 to
b9be0c4
Compare
|
Learn Build status updates of commit b9be0c4: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
#sign-off |
|
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @Mishih |
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
This PR updates documentation to reflect that RuntimeClaims JSON field names are kebab-case (not snake_case), correcting the table entries for VM configuration and user data fields.
Changes:
- Updated
vm_configuration→vm-configurationin the JSON field table - Updated
user_data→user-datain the JSON field table
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@mingweishih We will merge this PR. GitHub didn't accept your sign off because your Microsoft alias is listed in both the |
The JSON field names of the RuntimeClaims are kebab-case, not snake_case. This PR fixes the JSON names in the table.